I should add that the text2workspace step crashes on glados when using expr for WCs, but it runs on lxplus. We will need to debug this in the future.

Codecov Report

Attention: Patch coverage is 96.00000% with 1 line in your changes missing coverage. Please review.

Project coverage is 25.64%. Comparing base (3471b74) to head (8e1c1fd).

@@            Coverage Diff             @@
##           master     #458      +/-   ##
==========================================
+ Coverage   25.29%   25.64%   +0.35%     
==========================================
  Files          31       31              
  Lines        4977     5002      +25     
==========================================
+ Hits         1259     1283      +24     
- Misses       3718     3719       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Interesting, how does this deal with the decomposition step? i.e. where we break up the parameterization into separate "sub-"processes in order to encode the WC dependence.

Interesting, how does this deal with the decomposition step? i.e. where we break up the parameterization into separate "sub-"processes in order to encode the WC dependence.

We don't do that anymore with IM, everything is just stored in the scaling file. If we wanted to do something similar in AAC, it would probably still be casting the "new" WCs as functions of the "old".

Interesting, how does this deal with the decomposition step? i.e. where we break up the parameterization into separate "sub-"processes in order to encode the WC dependence.

We don't do that anymore with IM, everything is just stored in the scaling file. If we wanted to do something similar in AAC, it would probably still be casting the "new" WCs as functions of the "old".

Ah that's right, sorry! That does make things a lot simpler.

Looking at the code, I'm trying to understand what's going on in the block where you open/load the yaml file. My naive understanding is that the yaml file is mean to basically define a set of equations/functions whose arguments are purely WCs of the other basis, so when combine does the minimization in terms of those WCs the effect gets translated into the appropriate scaling in terms of the new/other WCs. What I don't get is all this manipulation you then need to do after you've loaded the yaml file. I also don't understand the use of eval in this block of code.

Interesting, how does this deal with the decomposition step? i.e. where we break up the parameterization into separate "sub-"processes in order to encode the WC dependence.

We don't do that anymore with IM, everything is just stored in the scaling file. If we wanted to do something similar in AAC, it would probably still be casting the "new" WCs as functions of the "old".

Ah that's right, sorry! That does make things a lot simpler.

Looking at the code, I'm trying to understand what's going on in the block where you open/load the yaml file. My naive understanding is that the yaml file is mean to basically define a set of equations/functions whose arguments are purely WCs of the other basis, so when combine does the minimization in terms of those WCs the effect gets translated into the appropriate scaling in terms of the new/other WCs. What I don't get is all this manipulation you then need to do after you've loaded the yaml file. I also don't understand the use of eval in this block of code.

The manipulations were my (probably inefficient) way to keep things general. I saved the cosine of the Weinberg angle as CW instead of hard coding it. The eval call is to compute SW.